Revision: ucf--devel--0.1--patch-72
Archive: srivasta@debian.org--2003-primary
Creator: Manoj Srivastava <srivasta@debian.org>
Date: Fri Mar 18 12:47:32 CST 2005
Standard-date: 2005-03-18 18:47:32 GMT
Modified-files: ucf ucf.1
New-patches: srivasta@debian.org--2003-primary/ucf--devel--0.1--patch-72
Summary: Fix a grave bug in ucf
Keywords: 

* ucf: Make sure that debconf-loadtemplate exists before calling it

* ucf.1 (needed): Added information about the inability of ucf to load
  its templates when the debconf DB gets corrupt. If the debconf database
  has been removed, or corrupted, debconf does not automatically install
  ucf templates, since usually the calling pattern is such that ucf is
  called from the maintainer script of another package. If the other
  package has already invoked debconf, then ucf uses the existing front
  end, which has already loaded the debconf database, installing the
  templates of that calling package. The ucf templates are not loaded
  automatically, since the front‐end script has no idea that they should
  be, it just heuristi‐cally loads the templates of the package whose
  maintainer scripts are being run.  In this scenario, ucf cannot load
  its templates, since the front‐end script shall override the database
  when it exits, and there is no way to tell the front‐end script to now
  load ucf templates on the fly. In this case, since the DB was corrupt,
  debconf can not find ucf templates.  In case no debconf front‐end is
  running, though, ucf tries hard to load its own templates, as long as
  the package debconf‐utis is installed. The only reliable way to reload
  ucf templates is to call
      dpkg‐reconfigure ucf


